Skip to content

feat: copy keydelim from parent chart in viper.Sub()#1887

Merged
sagikazarmark merged 1 commit intospf13:masterfrom
obs-gh-alexlew:copy-key-delim-for-sub
Jul 23, 2024
Merged

feat: copy keydelim from parent chart in viper.Sub()#1887
sagikazarmark merged 1 commit intospf13:masterfrom
obs-gh-alexlew:copy-key-delim-for-sub

Conversation

@obs-gh-alexlew
Copy link
Contributor

@obs-gh-alexlew obs-gh-alexlew commented Jul 22, 2024

Addresses #871

Simply copies the keyDelim from the parent chart to the subchart when calling viper.Sub(). Since there's currently no way to change the keyDelim of a viper instance post-creation, this is the only way to ensure that the sub viper instance maintains the keyDelim.

@CLAassistant
Copy link

CLAassistant commented Jul 22, 2024

CLA assistant check
All committers have signed the CLA.

@github-actions
Copy link

👋 Thanks for contributing to Viper! You are awesome! 🎉

A maintainer will take a look at your pull request shortly. 👀

In the meantime: We are working on Viper v2 and we would love to hear your thoughts about what you like or don't like about Viper, so we can improve or fix those issues.

⏰ If you have a couple minutes, please take some time and share your thoughts: https://forms.gle/R6faU74qPRPAzchZ9

📣 If you've already given us your feedback, you can still help by spreading the news,
either by sharing the above link or telling people about this on Twitter:

https://twitter.com/sagikazarmark/status/1306904078967074816

Thank you! ❤️

@sagikazarmark sagikazarmark added the kind/bug Something isn't working label Jul 23, 2024
@sagikazarmark sagikazarmark merged commit 864a85a into spf13:master Jul 23, 2024
@obs-gh-alexlew obs-gh-alexlew deleted the copy-key-delim-for-sub branch July 23, 2024 18:00
@NathanNam
Copy link

Great! When could we expect to see a new version with this change?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants